Skip to content

Conversation

@michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Aug 29, 2025

Resolves #18208

Summary by CodeRabbit

  • Documentation

    • Updated Google Ads documentation links and example endpoints from v18 to v21 across actions, sources, and app descriptions; refreshed prop descriptions and alerts to reference current v21 RPC docs for user lists, reporting, offline conversions, lead forms, and campaigns.
  • Chores

    • Bumped component and action versions to reflect documentation updates; no functional or public API changes.

@vercel
Copy link

vercel bot commented Aug 29, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
pipedream-docs Ignored Ignored Aug 29, 2025 9:49pm
pipedream-docs-redirect-do-not-edit Ignored Ignored Aug 29, 2025 9:49pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 29, 2025

Walkthrough

Google Ads integration updated from v18 to v21: internal endpoint paths, documentation links, example README, and action/source metadata were revised; package and action/source versions were bumped. No runtime logic, control flow, or public API signatures were changed.

Changes

Cohort / File(s) Summary of Changes
Core app endpoints & props
components/google_ads/google_ads.app.mjs
Updated internal API paths and path strings from v18 → v21; refreshed prop documentation links/descriptions to v21. No signature or control-flow changes.
Actions: docs/links & metadata
components/google_ads/actions/common/props.mjs, components/google_ads/actions/create-customer-list/common-constants.mjs, components/google_ads/actions/create-customer-list/create-customer-list.mjs, components/google_ads/actions/create-report/create-report.mjs, components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs, components/google_ads/actions/add-contact-to-list-by-email/add-contact-to-list-by-email.mjs
Switched documentation URLs and descriptive strings from v18 → v21 (RPC/REST as appropriate); bumped action versions and updated descriptions. No runtime logic changes.
Sources: docs & metadata
components/google_ads/sources/new-campaign-created/new-campaign-created.mjs, components/google_ads/sources/new-lead-form-entry/new-lead-form-entry.mjs
Updated descriptions and embedded docs links to v21; bumped versions. No behavioral changes.
Documentation example
components/google_ads/README.md
Example request URL updated from /v18/.../v21/....
Package metadata
components/google_ads/package.json
Package version bumped from 0.3.20.3.3.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Assessment against linked issues

Objective Addressed Explanation
Upgrade Google Ads API endpoints to v21 across components/google_ads/* (#18208)
Update in-app docs/prop descriptions to reference v21 docs (#18208)
Refresh actions/sources descriptions to v21 and bump versions as needed (#18208)
Update README examples to show v21 paths (#18208)

Poem

I twitched my nose at v18’s old sun,
Hopped to v21—update done!
Links refreshed, versions bright,
Endpoints nudged to newer light.
Thump-thump—deploys hum, rabbit delight. 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch issue-18208

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (6)
components/google_ads/actions/add-contact-to-list-by-email/add-contact-to-list-by-email.mjs (1)

34-36: Normalize email before hashing for Customer Match compliance.

Google requires trimming + lowercasing prior to SHA-256; current code hashes raw input, reducing match rate and risking policy noncompliance.

Apply:

   async run({ $ }) {
     const {
       googleAds, accountId, customerClientId, contactEmail, userListId,
     } = this;
+    const normalizedEmail = String(contactEmail).trim().toLowerCase();
@@
               userIdentifiers: [
                 {
-                  hashedEmail: crypto.createHash("sha256").update(contactEmail)
-                    .digest("hex"),
+                  hashedEmail: crypto.createHash("sha256")
+                    .update(normalizedEmail, "utf8")
+                    .digest("hex"),
                 },
               ],

Also applies to: 60-63

components/google_ads/README.md (4)

24-24: Fix typo: “interal” → “internal”.

-The Pipedream components interact with Google Ads API through an interal proxy service, which protects Pipedream's developer token.
+The Pipedream components interact with Google Ads API through an internal proxy service, which protects Pipedream's developer token.

49-59: Update example to v21 for consistency.

Example still points to v16; this PR upgrades to v21.

 const googleAdsReq = {
   method: "post",
-  url: "/v16/customers/1234567890/googleAds:search",
+  url: "/v21/customers/1234567890/googleAds:search",
   headers: {
     Authorization: `Bearer ${this.googleAds.$auth.oauth_access_token}`,
   },
   data: {
     query: "SELECT campaign.id, campaign.name FROM campaign",
   },
 };

86-107: Align Connect SDK example with v21.

         url: "/v19/customers:listAccessibleCustomers",
+        // v21 upgrade
+        // url: "/v21/customers:listAccessibleCustomers",

If you prefer a direct change:

-        url: "/v19/customers:listAccessibleCustomers",
+        url: "/v21/customers:listAccessibleCustomers",

113-122: Align Connect REST example with v21.

   -d '{
-    "url": "/v19/customers:listAccessibleCustomers",
+    "url": "/v21/customers:listAccessibleCustomers",
     "method": "GET",
     # "data": {} # If you need to send a body with a POST request, define it here
   }'
components/google_ads/package.json (1)

15-18: Remove redundant “crypto” dependency (prefer Node core).

Node’s built-in crypto shadows the npm “crypto” package; keeping the npm dep is unnecessary and a supply-chain risk.

   "dependencies": {
-    "@pipedream/platform": "^3.0.3",
-    "crypto": "^1.0.1"
+    "@pipedream/platform": "^3.0.3"
   }
🧹 Nitpick comments (3)
components/google_ads/actions/create-customer-list/common-constants.mjs (1)

201-209: Centralize the v21 docs base to ease future upgrades.

Reduce maintenance by defining a shared base like const GA_RPC_V21 = "https://developers.google.com/google-ads/api/reference/rpc/v21/"; and composing links.

Also applies to: 215-233

components/google_ads/sources/new-lead-form-entry/new-lead-form-entry.mjs (2)

10-10: Tighten the description and keep the helpful link.

Minor phrasing nit; also keep the same URL.

-  description: "Emit new event for new leads on a Lead Form. [See the documentation](https://developers.google.com/google-ads/api/reference/rpc/v21/GoogleAdsService/Search?transport=rest)",
+  description: "Emit an event when a new lead is submitted via a Lead Form. [See the v21 Search (REST) docs](https://developers.google.com/google-ads/api/reference/rpc/v21/GoogleAdsService/Search?transport=rest).",

32-32: Doc links updated correctly; consider de-duping the version string to reduce future churn.

Optional: define a single docs version token and interpolate into both links here (and the description) to simplify the next upgrade.

Example (outside this hunk, near the top of file):

const DOCS_VER = "v21";

Then update strings to:

content: `If needed, see Google's documentation on [submission fields](https://developers.google.com/google-ads/api/reference/rpc/${DOCS_VER}/LeadFormSubmissionField) and [custom submission fields](https://developers.google.com/google-ads/api/reference/rpc/${DOCS_VER}/CustomLeadFormSubmissionField).`,
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 59b21cc and 678496d.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (11)
  • components/google_ads/README.md (1 hunks)
  • components/google_ads/actions/add-contact-to-list-by-email/add-contact-to-list-by-email.mjs (1 hunks)
  • components/google_ads/actions/common/props.mjs (1 hunks)
  • components/google_ads/actions/create-customer-list/common-constants.mjs (5 hunks)
  • components/google_ads/actions/create-customer-list/create-customer-list.mjs (2 hunks)
  • components/google_ads/actions/create-report/create-report.mjs (4 hunks)
  • components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs (2 hunks)
  • components/google_ads/google_ads.app.mjs (9 hunks)
  • components/google_ads/package.json (1 hunks)
  • components/google_ads/sources/new-campaign-created/new-campaign-created.mjs (2 hunks)
  • components/google_ads/sources/new-lead-form-entry/new-lead-form-entry.mjs (2 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs (1)
components/google_ads/actions/common/props.mjs (2)
  • getAdditionalFields (4-9)
  • getAdditionalFields (4-9)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Lint Code Base
  • GitHub Check: pnpm publish
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Verify TypeScript components
🔇 Additional comments (11)
components/google_ads/actions/common/props.mjs (1)

2-2: Docs link updated to v21 — LGTM.

components/google_ads/package.json (1)

3-3: Package version bump is fine.

components/google_ads/sources/new-campaign-created/new-campaign-created.mjs (1)

9-10: v21 doc links and version bump look good.

No logic changes; references resolve to v21.

Also applies to: 22-22

components/google_ads/actions/create-report/create-report.mjs (2)

21-22: Doc links updated to v21 — looks good.

References now point to RPC v21 for Search, Fields, Segments, and Metrics.

Also applies to: 46-46, 109-110, 120-121


46-46: All resourceOption.value slugs resolve to valid v21 Fields docs (HTTP 200).

components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs (1)

23-27: Doc links and version bump align with v21.

Both the type link and additionalFields docs now target RPC v21.

components/google_ads/actions/create-customer-list/common-constants.mjs (1)

60-61: Docs migrated to RPC v21 — approved.

All updated references (CrmBasedUserListInfo, FlexibleRuleUserListInfo, UserListLogicalRuleInfo, ConversionAction, RemarketingAction, and type option docs) now point to v21.

Also applies to: 77-78, 87-88, 95-96, 118-119, 201-209, 215-233

components/google_ads/google_ads.app.mjs (1)

37-37: Prop doc references updated to v21.

Account, customer client, and lead form references look correct.

Also applies to: 49-50, 74-75

components/google_ads/actions/create-customer-list/create-customer-list.mjs (2)

17-18: Top-level docs + version updated to v21 — approved.


36-36: List type docs now point to RPC v21 — approved.

components/google_ads/sources/new-lead-form-entry/new-lead-form-entry.mjs (1)

11-11: Google Ads docs/wiring updated to v21
No pre-v21 RPC links found and google_ads.app.mjs exclusively references v21.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
components/google_ads/google_ads.app.mjs (1)

120-131: Update hardcoded API version and verify GAQL v21 field compatibility

  • README.md still references /v19/customers:listAccessibleCustomers on lines 100 and 118; change both to /v21/customers:listAccessibleCustomers.
  • GAQL queries in components/google_ads show no obvious deprecated fields (e.g., shared_set, user_list_size_range), but manually confirm that all SELECT/FROM/WHERE clauses in your QUERIES.* functions use valid v21 resource and field names.
♻️ Duplicate comments (2)
components/google_ads/google_ads.app.mjs (2)

229-229: Normalize HTTP method casing to match the rest of this file.

You mix "post" and "POST". Standardize to one form (recommend "post" to match other calls and prior review guidance).

-        method: "POST",
+        method: "post",
@@
-        method: "POST",
+        method: "post",
@@
-        method: "POST",
+        method: "post",

Also applies to: 236-236, 245-245


124-124: De-duplicate the API version string with a constant.

Avoid scattering "v21" literals; it simplifies the next upgrade and reduces copy/patch errors.

@@
 import { QUERIES } from "./common/queries.mjs";
 
+const API_VERSION = "v21";
+
@@
-        path: "/v21/customers/{customerClientId}/googleAds:search",
+        path: `/${API_VERSION}/customers/{customerClientId}/googleAds:search`,
@@
-        path: "/v21/customers:listAccessibleCustomers",
+        path: `/${API_VERSION}/customers:listAccessibleCustomers`,
@@
-        path: "/v21/customers/{customerClientId}/userLists:mutate",
+        path: `/${API_VERSION}/customers/{customerClientId}/userLists:mutate`,
@@
-        path: "/v21/customers/{customerClientId}/conversionActions:mutate",
+        path: `/${API_VERSION}/customers/{customerClientId}/conversionActions:mutate`,
@@
-        path: `/v21/${path}:addOperations`,
+        path: `/${API_VERSION}/${path}:addOperations`,
@@
-        path: "/v21/customers/{customerClientId}/offlineUserDataJobs:create",
+        path: `/${API_VERSION}/customers/{customerClientId}/offlineUserDataJobs:create`,
@@
-        path: `/v21/${path}:run`,
+        path: `/${API_VERSION}/${path}:run`,

Also applies to: 135-135, 154-154, 219-219, 231-231, 238-238, 247-247

🧹 Nitpick comments (2)
components/google_ads/google_ads.app.mjs (2)

135-136: Be explicit about the proxied HTTP method.

listAccessibleCustomers omits method. If the proxy defaults ever change, this could break. Set method: "get" explicitly.

-      const response = await this._makeRequest({
-        path: "/v21/customers:listAccessibleCustomers",
-      });
+      const response = await this._makeRequest({
+        method: "get",
+        path: "/v21/customers:listAccessibleCustomers",
+      });

231-231: Guard against callers passing a versioned sub-path.

If a caller accidentally includes vXX/ in path, you'll end up with .../v21/v21/.... Consider stripping any leading version segment.

-        path: `/${API_VERSION}/${path}:addOperations`,
+        path: `/${API_VERSION}/${String(path).replace(/^\/?v\d+\//, "")}:addOperations`,
@@
-        path: `/${API_VERSION}/${path}:run`,
+        path: `/${API_VERSION}/${String(path).replace(/^\/?v\d+\//, "")}:run`,

Also applies to: 247-247

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 678496d and fb8f5f1.

📒 Files selected for processing (2)
  • components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs (2 hunks)
  • components/google_ads/google_ads.app.mjs (9 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/google_ads/actions/send-offline-conversion/send-offline-conversion.mjs
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Lint Code Base
🔇 Additional comments (2)
components/google_ads/google_ads.app.mjs (2)

124-124: v21 path upgrades look correct and consistently use a leading “/”.

Good alignment with the proxy and RPC-style endpoints. No functional concerns on these path updates.

Also applies to: 135-135, 154-154, 219-219, 231-231, 238-238, 247-247


37-37: Doc links updated to RPC v21 look good.

Links resolve to the correct RPC resources; nice touch for DX.

Also applies to: 49-49, 74-74

Copy link
Collaborator

@GTFalcao GTFalcao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@vunguyenhung vunguyenhung merged commit 4e64451 into master Sep 1, 2025
10 checks passed
@vunguyenhung vunguyenhung deleted the issue-18208 branch September 1, 2025 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Google Ads components use a deprecated API version — please upgrade to Google Ads API v21

4 participants